home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-05
/
lstn1-5.zip
/
LS-4.TXT
< prev
next >
Wrap
Text File
|
1991-10-03
|
8KB
|
244 lines
Hayes(r) Microcomputer Products, Inc. LANstep(r) Technical Note
"Using DOS 5.0 on the NSS"
Number LS-4 September 1991
Summary:
This Technical Note
* explains how to use the Microsoft DOS 5.0 upgrade kit or IBM DOS
5.0 on your NSS.
* provides examples of high-memory usage that is available with DOS
5.0.
What's Required?
To use DOS 5.0 with LANstep, you'll need to decide if you want to
install DOS 5.0 on the NSS (to provide DOS 5.0 to all network booted
workstations), or just on a locally booted DOS Workstation.
If you want to install DOS 5.0 on the NSS, you'll need:
* the DOS 5.0 Upgrade Kit
* LANstep 1.0B or newer
IMPORTANT: You must install LANstep 1.0B before installing DOS 5.0.
LANstep Update 1.0B may be obtained via Hayes Customer Service (404)
441-1617 (US) or (519) 746-5000 (Canada).
If you only wish to run DOS 5.0 on a locally booted DOS Workstation,
you must have:
* the DOS 5.0 upgrade kit
* LANstep 1.0A or newer
Note: You don't have to upgrade beyond version 1.0A of LANstep if
you only want to install DOS 5.0 on a locally booted DOS Workstation.
IMPORTANT: This Upgrade 1.0B should not be installed while Network
Booted DOS Workstations are logged into the network, as an error may
occur if the workstation attempts to reload the command interpreter,
expecting the old version. You should logout first, then go ahead
with the procedure.
Installing DOS 5.0 on the NSS
To install DOS 5.0 on your NSS, you must first create a working boot
diskette; follow these steps:
Step 1:
A series of diskettes are provided with the DOS 5.0 upgrade
kit. Locate disk #1, place it in drive A: of the NSS. Move to the
DOS prompt of the NSS (if not there already) and type:
A:\SETUP /f
This process requires multiple diskettes. You should have at least
7, 5 1/4 and 4, 3 1/2 diskettes; they do not have to be formatted
before use.
Next, you need to start up without using the drivers that load in
the CONFIG.SYS file of the STARTUP or STARTUP / SUPPORT diskette.
You can do this by renaming the CONFIG.SYS file that is created with the
DOS upgrade,.so the CONFIG.SYS is not loaded when the Install DOS
icon is selected.
Step 2:
Renaming CONFIG.SYS does two things: first, a rename doesn't
change the original file, so it can be renamed again when needed
and not recreated. Second, by not having a CONFIG.SYS, DOS won't load the
drivers that interfere with the NSS. Insert the STARTUP or STARTUP
/ SUPPORT diskette into floppy drive A and enter:
REN A:\CONFIG.SYS CONFIG.500
If DOS is Not Already Installed on the NSS
If DOS (any version) is not installed on the NSS, you can simply go
to the Setup room and select Install DOS, following the prompts.
However, if DOS is already installed on the NSS, you'll need to
remove the old version before installing DOS 5.0.
Removing Old DOS Files
You can remove almost all the existing DOS files with a DEL command,
but there are some DOS files that must have their attributes changed
before they can be deleted from a DOS prompt. You can use any other
DOS utility (such as XTREE PRO or Norton's) to change these
attributes so these files can be deleted. Or, you can use the
Browser; here's how:
Note: In this instance, we're using the Browser to delete the two
DOS files that have the READ-ONLY, HIDDEN and SYSTEM attributes.
Step 1:
Go into the Support Room, and select Browse Hard Disk 0.
Step 2:
Select DOS, then press Enter.
Step 3:
Select BOOT and press Enter.Now, you'll need to access
extended commands; press Control-E.
Step 4:
Use Control-+ to expand the screen and show all the files.
For IBM DOS, find IBMBIO.COM and IBMDOS.COM. If you were using
Microsoft DOS, then the filenames are IO.SYS and MSDOS.SYS.
Highlight the files (one at a time), press F6 to remove, then F2 to confirm.
Step 5:
Press Escape to exit the Browser, then go to the Setup LAN
Room and select Install DOS on the NSS icon.
Step 6:
Follow the prompts to start DOS. When DOS starts, do not run
H:LSINSTAL yet.
Step 7:
Now delete the files on drive E: by typing:
DEL E:\*.*
Step 7:
Now you can run LSINSTAL from the A: drive; type:
H:LSINSTAL
and follow the prompts for further installation.
Rebinding Workstations
All Network booted DOS Workstations systems must be rebound at this
time, since a new version of DOS has been installed. Some customized
systems require additional time for this process to complete.
Step 1:
Use the Management Console to select LAN Configuration.
Step 2:
Select Network Booted DOS Workstation Systems.
Step 3:
Select the system name, then press F3:UPDATE. No changes
need to be made. Just press F3 to save and exit. Do not boot any
Network-Booted DOS Workstation until all systems have been
updated. Repeat for each system that requires the update.
Installing DOS 5.0 on a Locally Booted DOS Workstation
DOS 5.0 can be used on a locally booted DOS Workstation using
LANstep Version 1.0A or greater. However, there are some precautions
you should consider before proceeding.
* DOS creates a new AUTOEXEC.BAT and CONFIG.SYS on the boot drive,
but the workstation regeneration procedure updates them both to
install the proper commands to get the user back on the
LAN.
* When you generate the LANstep workstation procedure, the
PROTOCOL.INI file is replaced, and a backup, PROTOCOL.BAK is
created.
Running the DOS Installation Procedure
From the locally booted DOS workstation, use the DOS 5.0 diskettes
and the installation program to update the workstation's DOS system
files. This procedure installs DOS 5.0 on that workstation.
Since the installation of DOS 5.0 replaces the AUTOEXEC.BAT and
CONFIG.SYS, you'll need to run the workstation generation procedure
to update the files to work with LANstep.
Run the Workstation Generation Procedure
Install the Workstation Setup disk in drive B:, then type:
B: INSTALL
Just follow the prompts; when finished, a new PROTOCOL.INI is
created, so you'll need to replace it with your old one.
From the boot drive, type:
COPY PROTOCOL.BAK PROTOCOL.INI
Reboot the system by pressing Control+Alt+Del.
Using High Memory
An Intel 80386 or 80486 based computer that has extended memory and
is configured as a DOS Workstation can make use of EMM386.EXE, the
memory manager for DOS 5.0. LANstep will detect the existence of
Upper Memory Blocks, and load itself accordingly into the available
blocks.
The following example will allow you to load NETRDR (approx. 94K)
into Upper Memory Blocks (UMB)from your AUTOEXEC.BAT file. Use of the
LOADHIGH command will not be necessary.
FILES=25
BUFFERS=3
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS x=D800-DC00
DOS=HIGH
DEVICE=PROTMAN.SYS
DEVICE=NDISDRVR.SYS
The x switch in the EMM386 line is used to exclude a particular
memory area from the memory manager. In this case, we are assuming a
Hayes Ethermate Trio 16 card, which uses a 16K block of memory for
interfacing with the network. For more information about the x
switch, see the chapter on device drivers in your DOS user's guide.
Some computer manufacturers do not allow the UMB area to be
manipulated by DOS. Again, refer to your DOS user's guide for more
information about memory management.
Hayes is a registered trademark and LANstep is a trademark of Hayes
Micrcomputer Products, Inc.
Other trademarks appearing in this document are trademarks of the
respective companies
(C) 1991 Hayes Microcomputer Products, Inc.